SQL Server must protect the SQL Server audit tool or any other third-party audit tools from unauthorized deletion.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-41018	SQL2-00-014100	SV-53393r1_rule		Medium

Description
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized access. Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys in order to make decisions regarding access to audit tools. Audit tools include, but are not limited to, OS-provided audit tools, vendor-provided audit tools, and open-source audit tools needed to successfully view and manipulate audit information system activity and records. If an attacker were to gain access to audit tools, they could analyze audit logs for system weaknesses or weaknesses in the auditing itself. An attacker could also manipulate logs to hide evidence of malicious activity.

Description

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized access. Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys in order to make decisions regarding access to audit tools. Audit tools include, but are not limited to, OS-provided audit tools, vendor-provided audit tools, and open-source audit tools needed to successfully view and manipulate audit information system activity and records. If an attacker were to gain access to audit tools, they could analyze audit logs for system weaknesses or weaknesses in the auditing itself. An attacker could also manipulate logs to hide evidence of malicious activity.

STIG	Date
Microsoft SQL Server 2012 Database Instance Security Technical Implementation Guide	2014-06-23

Details

Check Text ( C-47635r2_chk )
Obtain the SQL Server software library installation directory location. From a command prompt, type regedit.exe, and press [ENTER]. Each instance will have its own registry tree at the following registry location: HKEY_LOCAL_MACHINE >> SOFTWARE >> Microsoft >> Microsoft SQL Server >> [INSTANCE NAME]. An [INSTANCE NAME] is listed as the data component of a key found in one of the above OLAP, RS, or SQL folders. To find the installation location of a particular instance, navigate to the following location in the Windows Registry: HKEY_LOCAL_MACHINE >> SOFTWARE >> Microsoft >> Microsoft SQL Server >> [INSTANCE NAME] >> Setup. Examine the value of the 'SqlProgramDir' key. The value of the 'SqlProgramDir' key is the SQL Server installation directory for that SQL Server instance. Navigate to that folder location using a command prompt or Windows Explorer. Verify that files and folders that are part of the SQL Server 2012 installation have only the following privileges: Right click each folder under the installation folder, click Properties. On the Security tab, verify only the following permissions are present. ...\MSSQL\backup – SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control) ...\MSSQL\binn – SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control) ...\MSSQL\data– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control) ...\MSSQL\FTData– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control) ...\MSSQL\Install– SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control) ...\MSSQL\Log– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control) ...\MSSQL\Repldata– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control) 110\shared– SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control) If additional permissions are present, this is a finding.

Check Text ( C-47635r2_chk )

Obtain the SQL Server software library installation directory location.

From a command prompt, type regedit.exe, and press [ENTER]. Each instance will have its own registry tree at the following registry location: HKEY_LOCAL_MACHINE >> SOFTWARE >> Microsoft >> Microsoft SQL Server >> [INSTANCE NAME].

An [INSTANCE NAME] is listed as the data component of a key found in one of the above OLAP, RS, or SQL folders.

To find the installation location of a particular instance, navigate to the following location in the Windows Registry:
HKEY_LOCAL_MACHINE >> SOFTWARE >> Microsoft >> Microsoft SQL Server >> [INSTANCE NAME] >> Setup. Examine the value of the 'SqlProgramDir' key. The value of the 'SqlProgramDir' key is the SQL Server installation directory for that SQL Server instance.

Navigate to that folder location using a command prompt or Windows Explorer.

Verify that files and folders that are part of the SQL Server 2012 installation have only the following privileges:
Right click each folder under the installation folder, click Properties. On the Security tab, verify only the following permissions are present.

...\MSSQL\backup – SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control)
...\MSSQL\binn – SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control)
...\MSSQL\data– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control)
...\MSSQL\FTData– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control)
...\MSSQL\Install– SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control)
...\MSSQL\Log– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control)
...\MSSQL\Repldata– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control)
110\shared– SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control)

If additional permissions are present, this is a finding.

Fix Text (F-46317r2_fix)
Navigate to the SQL Server software library directory folder location. Right click the file/folder, click Properties On the Security tab, modify the security permissions, verify that files and folders that are part of the SQL Server 2012 installation have only the following privileges: Right click each folder under the installation folder, click Properties. On the Security tab, verify only the following permissions are present. …\MSSQL\backup – SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control) …\MSSQL\binn – SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control) …\MSSQL\data– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control) …\MSSQL\FTData– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control) …\MSSQL\Install– SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control) …\MSSQL\Log– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control) …\MSSQL\Repldata– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control) 110\shared– SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control)

Fix Text (F-46317r2_fix)

Navigate to the SQL Server software library directory folder location.

Right click the file/folder, click Properties

On the Security tab, modify the security permissions, verify that files and folders that are part of the SQL Server 2012 installation have only the following privileges:
Right click each folder under the installation folder, click Properties. On the Security tab, verify only the following permissions are present.

…\MSSQL\backup – SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control)
…\MSSQL\binn – SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control)
…\MSSQL\data– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control)
…\MSSQL\FTData– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control)
…\MSSQL\Install– SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control)
…\MSSQL\Log– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control)
…\MSSQL\Repldata– SqlServerService Account (Full Control), System (Full control), System Administrators (Full Control)
110\shared– SqlServerService Account (Read, Execute), System (Full control), System Administrators (Full Control)